|
|
|
Figure 1 shows a typical system-wide network diagram that includes Avaya IP Telephones, Avaya Communication Manager Servers, and application servers. The application servers include Push Servers, Subscription Servers, and a Web Application Server.
Figure 1: Typical System-Wide Network Topolgy
With this picture in the current context, enabling a Web server or an application server for a particular enterprise is not an additional entity.
Example:ABC Company currently has an intranet Web server that serves the company’s intranet sites and other employee information. ABC has just deployed a company-wide Avaya IP Telephone system, which offers an optional Web browser application. To set up a Web server for the Avaya IP Telephones, ABC just has to add two MIME types to their existing intranet Web server. ABC does not require an additional server or entity to enable Web functionality on Avaya 9600 Series IP Telephones. Additionally, the same intranet server can be a Push Application server or a Trusted Push Server. Similarly, a subscription server can also be resident on ABC’s existing intranet server. NOTE: For more information on setting up MIME types or setting up a Web server, see the WML Server Setup Guide (Document Number16-300507), available for download at: http://www.avaya.com/support. |
|
|
|
